ci: auto-deploy to stage on merge to main - #85
Merged
Conversation
louisachu
approved these changes
Sep 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
dev-docs-referenceis only exposed on stage in Fastly (developer-stage.adobe.com/dev-docs-reference), not prod. But the deploy workflow fires on merge tomainwithenv: 'prod', so changes never showed up on developer-stage — someone had to manually trigger theStagingworkflow after every merge.Fix
Change the push-to-
maindefault env indeploy.ymlfrom'prod'to'stage & prod', so a single run deploys to both and the manual step is gone.Greenlit by Shikhar (Sept 1 team meeting).